You are here: Revised Table Definitions > FO_IF_Translations

FO_IF_Translations

This table allows the User to specify translation values for external data arriving through the Client Data Concentrator interfaces (CDC).

Each record represents a particular field type of foreign and native values for a MPI qualifier and Interface code. An interface code is assigned in the config file of the comms and processor jobs of an interface.

 

Field

Type

Notes

FO_IF_Translations_ID

int

Identity (counter) field

InterfaceCode

varchar(50)

Interface code for this translation. The interface code is defined in the Comms and Processor jobs config files.

TranslationType

varchar(50)

Single character that represents a translation type.

I = insurance P = provider
C = client B = bill to
T = test code L = patient location
G = gender R = relationship value
S = species PR = priority
M = marital  

ForeignValue

varchar(50)

Value for this type in the external system.

FPValue

varchar(50)

Value to translate to in FP.

For type I insurance translations, if the FPValue is listed as "*DNU*", then the system will not record any insurances from that message.

The system will still force the billto if the above field is valued. (force it to what?)

This is only honored for the primary insurance (first IN1) segment in a message.

MPIQualifier

varchar(50)

MPI qualifier code.

CreateDate

datetime

Date record was created. Informational

CreatedBy

varchar(50)

User who created the record. Informational

EditDate

datetime

Date record was edited. Informational

EditedBy

varchar(50)

User who last edited the record. Informational

ForceBillTo

Varchar(50)

Defines the billto value for every order created by reference to this translation.

Only applies to translation type I insurance for the first IN1 segment.

This will override what was sent in message or default value for qualifier.

Use a valid FAST billto value. See billto table for valid entries of longcode.

This logic will be used only if the translation rules are activated to cause the system to translate the insurance code in the message.

An IN1 segment must have at least an insurance code and a policy number to qualify as a valid segment. If it does not, no translation will be applied.